Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 16 OCTOBER 1978 (Cancels and replaces HCOB 21 Dec 75R Repair List for Prepared Lists.) | Saint Hill Manor, East Grinstead, Sussex HCO BULLETIN OF 16 OCTOBER 1978 Issue II |
REPAIR CORRECTION LIST | CS Series 102 |
Use this list to clean up bypassed charge on improperly done or unnecessary prepared lists or repair actions. This list is done when a pc protests a prepared list or repair action, when BIs are present on the subject of repair or prepared lists or when improper past repair or use of correction lists reads on a correction list. | C/S CHECKLIST OF INT ERRORS |
Assess this list Method 5 and handle all reads. The EP of this list is charge off the subject of repair and prepared lists and the pc happy about being audited. This list can, if necessary, be reassessed and taken to an F/Ning assessment. | There are two major errors that occur most frequently on Int handling which a C/S must be on the alert for: |
The words “prepared list,” “repair” and all other words on this list should be fully cleared with the pc before assessing this list on him. However, if the pc is very upset and the words have not yet been cleared, assess the list to handle the charge and check with the pc for any MUs on the assessment. (Ref: HCOB 9 Aug 78 II CLEARING COMMANDS) | 1. Doing or running anything else before an Int Rundown when one is needed. |
2. Overrunning the Int Rundown. | |
By far the commonest error is number one above. It happens most often at the very beginning of a session on Int itself, by the auditor engaging in two-way comm or ruds or a belabored and overcomplicated clearing of commands, or some other action than getting right onto the running of Int. | |
| 1. | This is flagrant. When I was C/Sing, it is what I kept running into – the auditor doing all kinds of preliminary steps before starting Int. It boils down to auditing over out-Int, and it can’t be done. |
| Have you gone exterior in auditing? If the pc has never had an Int RD, do an Int RD per HCOB 4 Jan 71R Int RD Series 2 EXTERIORIZATION AND HIGH TA THE INT RD REVISED if you have checked out on the Int Series and are a NED auditor. If the pc has had an Int RD, do an Int RD Correction List Revised (HCOB 29 Oct 71RA) or end off for C/S instructions to do an End of Endless Int Repair RD per HCOB 24 Sep 78 I URGENT IMPORTANT END OF ENDLESS INT REPAIR RD. | You’ll get the auditor who says, “But all I did was ask him how he was feeling.” That’s enough. That’s two-way comm, and you can’t run anything else but Int when Int is out, and that includes two-way comm. You don’t ask the pc how he feels about anything. You just start the Int Rundown. |
| _____________ | So that’s the first major error to watch for: somebody trying to run something else before the Int Rundown itself. |
The second is overrun. Pc has a big cognition, a big win, TA blowdown, and the auditor misses it, goes right on past it and continues auditing. Or the pc exteriorizes and the auditor continues past exterior. | |
| 2. | There is vital data on the end phenomena of Int on HCOB 4 Jan 71R, Int RD Series 2, and both C/S and auditor must have this data and know and be able to recognize the EP of Int when it occurs. Otherwise it will really mess up a case. |
| Has your INT RD been messed up? Do an Int RD Correction List or end off for C/S instructions to do the End of Endless Int Repair RD. | Those are the two major violations a C/S (and an auditor) must not permit in the running of Int if it is to be successful. |
| _____________ | Because they are the most major errors they have been included first on the checklist below. |
C/S CHECKLIST FOR DETECTING ERRORS ON INT: | |
| 3. | The following is a checklist to be used in the C/Sing of Int. The C/S checks a bogged session or any session on Int, against this list to detect the exact cause of the trouble, or an error that could be the source of future trouble in ensuing sessions. |
| Do you have an out-list? L4BRA. | 1. Doing or running anything else before an Int Rundown when one is needed. (Includes ruds, 2-way comm, L1C, anything.) |
| _____________ | 2. Auditing over out-Int. |
3. Overrunning the Int Rundown. | |
| 4. | 4. Auditing past exterior. |
| Have you had too many prepared lists done on you? Indicate. Itsa E/S itsa to F/N or Date/Locate the first successful prepared list. | 5. Overdoing the clearing steps preceding the actual rundown. |
| _____________ | 6. Running an Int button that only read on an MU or false read. (Failure to clear an Int button before running it.) |
7. Clearing all of the Int buttons before assessment, instead of clearing only the button with the largest valid read. | |
| 5. | 8. Failure to use Suppress, Invalidate, and Misunderstood on an unreading Int button list. |
| Have you had unnecessary repairs? Indicate. Itsa E/S itsa to F/N or Date/Locate the first valid repair. | 9. Misassessment of the Int button list. |
| _____________ | 10. Doing an Int Rundown when none of the buttons have read. (Constitutes running an unreading item.) |
11. Auditor can’t get reads or make a list read. | |
| 6. | 12. Not taking the Int Rundown to its full EP. |
| Has an auditor missed a read? Get what, itsa E/S itsa to F/N, or handle as needed. | 13. Not understanding the theory of Int and R3RA, and why one goes earlier or asks for an earlier beginning to the incident. |
| _____________ | 14. Running the concept of “was in” or “stuck in” instead of the concept of “moving in” or “going in” (on whatever the reading Int button is). |
15. Not repeating the actual button for the chain when asking for an earlier incident. (Not knowing R3RA commands.) | |
| 7. | 16. Not completing a chain to full Dianetic EP. |
| Did you think something should have read when it didn’t? Get what, itsa E/S itsa to F/N, or handle as needed. | 17. Not completing any one flow on an Int button in one session; thus ending a session on an unflat flow. |
| _____________ | 18. Introducing Flow 0 to a pc for the first time on Int Rundown or Int repair. (i.e. running a Triple pc on Quad Flows.) |
19. Auditing over an earlier Dianetic error. | |
| 8. | 20. Auditing the rundown “to exteriorize” the pc. |
| Has an item not read when it should have? Get what, itsa E/S itsa to F/N, or handle as needed. | 21. Using preassessment or AESPs on Int. |
| _____________ | 22. Misassessing or incorrectly handling the Int Correction List. |
23. Overcorrecting the Int Rundown. | |
| 9. | 24. Running Dianetics on a Dianetic Clear, Scn Clear or OT. |
| Has there been a false read? Indicate. Itsa E/S itsa to F/N. | 25. And, on the part of the C/S, attempting to correct a botched Int Rundown without a full FES of the Int RD or any Int repair being done first. |
| _____________ | |
The above points are all covered fully in the Int Rundown Series. Cases that are not running well on Int will be found to have had one or more of these errors committed on them. | |
| 10. | Using the above list to spot and prevent Int errors will make the C/S’s job lighter and give both auditor and pc a smoother run on Int. |
| Were you told something read when you didn’t see how it could have? Get what, indicate it was a false read. Itsa E/S itsa to F/N. | Founder |
| _____________ | |
| 11. | |
| Did the auditor take up an item with no charge on it? Indicate. Itsa E/S itsa to F/N. | |
| _____________ | |
| 12. | |
| Were you given a prepared list to handle high TA when your TA wasn’t high? Indicate. Itsa E/S itsa to F/N. | |
| _____________ | |
| 13. | |
| Were you given a prepared list to handle low TA when your TA wasn’t low? Indicate. Itsa E/S itsa to F/N. | |
| _____________ | |
| 14. | |
| Has there been a time when you didn’t want to do a prepared list and the auditor did one anyway? Indicate. Itsa E/S itsa to F/N. | |
| _____________ | |
| 15. | |
| Has there been a time when you didn’t want to get a repair action and you were given one anyway? Indicate. Itsa E/S itsa to F/N. | |
| _____________ | |
| 16. | |
| While being audited on a prepared list did you just want to get on with it? Indicate. Itsa E/S itsa to F/N. | |
| _____________ | |
| 17. | |
| Did you tell the auditor something was handled just to be done with it? Indicate. Itsa E/S itsa to F/N. Note for C/S. | |
| _____________ | |
| 18. | |
| Has overrepair kept you from going up the grade chart? Indicate. Itsa E/S itsa to F/N. | |
| _____________ | |
| 19. | |
| Have you been told a repair action would handle your case when it didn’t? Indicate. 2WC to F/N or 2WC for data. | |
| _____________ | |
| 20. | |
| Has an auditor misassessed a prepared list on you? Itsa E/S itsa to F/N. | |
| _____________ | |
| 21. | |
| When you had a prepared list done, did it fail to handle the bypassed charge? Itsa E/S itsa to F/N. | |
| _____________ | |
| 22. | |
| Did a repair action fail to handle what was really wrong? Itsa E/S itsa to F/N. | |
| _____________ | |
| 23. | |
| Have you been assessed by an auditor with bad TRs? Itsa E/S itsa to F/N. | |
| _____________ | |
| 24. | |
| Has an auditor told you you had an F/N when you knew you didn’t? Itsa E/S itsa to F/N. | |
| _____________ | |
| 25. | |
| Did an auditor ever indicate an assessment was F/Ning when you knew it wasn’t? Itsa E/S itsa to F/N. | |
| _____________ | |
| 26. | |
| Were you asked to declare a cycle you felt wasn’t complete? Itsa E/S itsa to F/N. | |
| _____________ | |
| 27. | |
| Did you ever feel a prepared list should have F/Ned on an assessment when it didn’t? Indicate. Rehab the EP or Date/Locate the point. | |
| _____________ | |
| 28. | |
| On a repair action, were you prevented from attesting? Indicate. Date/Locate the EP of the repair. | |
| _____________ | |
| 29. | |
| Has your repair been repaired often? Indicate. Itsa E/S itsa to F/N or Date/Locate the first successful repair. | |
| _____________ | |
| 30. | |
| Has an F/N been missed? Indicate. Rehab it. | |
| _____________ | |
| 31. | |
| Has a win been bypassed? Indicate. Rehab. | |
| _____________ | |
| 32. | |
| Has something been overrun? Get what. Rehab it. | |
| _____________ | |
| 33. | |
| Is there some other bypassed charge? Find what and handle. | |
| _____________ | |